This PR migrates our salt-master to run on Ubuntu 22.04, codename "Jammy."

In our previous configuration running salt 3004, the salt-master ran as the root user. In the latest release, the salt-master adds a "salt" user and group by default, and runs as the "salt" user. By adding user: root to out vagrant master.conf file, we allow the salt-master to run as root, like we had previously done, and bypass permissions errors related to loading ca.py and consul.py modules.

This PR also conditionally updates our configuration to use the onedir packaging with codename "jammy" updating the repo URL, path names, and GPG key.

To verify this locally:

1. bring up the salt-master, laptop:psf-salt user$ vagrant up salt-master
2. bring up the loadbalancer, laptop:psf-salt user$ vagrant up loadbalancer
3. bring up a backend service like hg, laptop:psf-salt user$ vagrant up hg

The traceback for the salt-master should show it running on jammy, but to further verify the upgrade:

1. in another window, ssh into the salt-master, laptop:psf-salt user$ vagrant ssh salt-master
2. run the command lsb_release -a

Distributor ID:	Ubuntu
Description:	Ubuntu 22.04.3 LTS
Release:	22.04
Codename:	jammy

Note:

• apt-key is deprecated with Ubuntu 22.04. The recommended approach is to configure -aptkey: False to the package repo state, and set signed-by in the repo name.

• This PR is currently in a state where all packages are updated to use this recommended approach except for postgresql.

• The current bug appears to happen when salt adds the postgresql gpg key to our designated signed by file, the file permissions are not set the _apt user to read.

-rw-r--r-- 1 root root 4538 Jan 12 13:52 datadoghq.gpg
-rw-r--r-- 1 root root 1067 Jan 12 13:52 nginx.gpg
-rw-r--r-- 1 root root 2820 Jan 12 13:51 packagecloud.gpg
-rw-r----- 1 root root 3494 Jan 12 13:52 postgresql.gpg

To learn more about this bug, see #333.